Positive slack means the modeled start can move later by that many calendar days before reaching the supplied latest start. Zero slack is commonly associated with critical work, but a reliable critical path comes from the full network, not a pair of manually chosen dates. Negative float can appear in professional schedules when a completion requirement is earlier than the network forecast; this page instead rejects a latest start before earliest start.
The GAO Schedule Assessment Guide explains that early dates come from a forward pass and late dates from a backward pass through network logic. Constraints, lags, calendars and broken relationships can make float misleading. Review the predecessor and successor chain before using slack to move resources.
Slack is a schedule property, not automatically time owned by one team. Consuming it can reduce flexibility for later work. Update the calculation when durations, dependencies or required completion dates change, and document whether reported values use calendar or working days.
When reporting slack, include the schedule status date and revision. The same activity can gain or lose float as progress is recorded, logic changes or another path becomes critical. A large number is not necessarily spare project time if it results from missing successors or a distant imposed constraint. Likewise, management may choose to preserve positive float as protection against uncertainty instead of deliberately consuming it. Use the two-date answer as a transparent check, then return to the integrated schedule to understand which relationships produced those dates and who is affected by a change. Confirm the calendar basis before publishing the number to a project report.
